SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>TPT (software)</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">TPT (software)</span></span>

</h1>

</header>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}

/* end https://en.wikipedia.org/ */

</style><table class="infobox vevent"><tbody><tr><th colspan="2" class="infobox-above summary">Time Partition Testing (TPT)</th></tr><tr><td colspan="2" class="infobox-image logo"></td></tr><tr><td colspan="2" class="infobox-image logo"><div class="infobox-caption">Test case modelled with TPT</div></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Programmer" title="Programmer">Developer(s)</a></th><td class="infobox-data">Synopsys Inc.</td></tr><tr style="display: none;"><td colspan="2" class="infobox-full-data"></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Software_release_life_cycle" title="Software release life cycle">Stable release</a></th><td class="infobox-data"><div style="margin:0px;">2024.12

/ December 2024<span style="display:none"> (<span class="bday dtstart published updated">2024-12</span>)</span></div></td></tr><tr style="display:none"><td colspan="2">

</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Operating_system" title="Operating system">Operating system</a></th><td class="infobox-data"><a href="Windows" class="mw-redirect" title="Windows">Windows</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;">Available in</th><td class="infobox-data">English</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Software_categories#Categorization_approaches" title="Software categories">Type</a></th><td class="infobox-data"><a href="Software_testing" title="Software testing">Software testing</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;"><a href="Software_license" title="Software license">License</a></th><td class="infobox-data"><a href="Proprietary_software" title="Proprietary software">Proprietary</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap;">Website</th><td class="infobox-data"><span class="url"><a rel="nofollow" class="external text" href="https://www.synopsys.com/verification/virtual-prototyping/tpt.html">www<wbr>.synopsys<wbr>.com<wbr>/verification<wbr>/virtual-prototyping<wbr>/tpt<wbr>.html</a></span></td></tr></tbody></table>

<p><b>TPT</b> (<b>time partition testing</b>) is a systematic <a href="Software_testing" title="Software testing">test</a> <a href="Methodology" title="Methodology">methodology</a> for the <a href="Test_automation" title="Test automation">automated</a> <a href="Software_testing" title="Software testing">software test</a> and <a href="Verification_and_validation" title="Verification and validation">verification</a> of <a href="Embedded_system" title="Embedded system">embedded control systems</a>, <a href="Cyber-physical_system" title="Cyber-physical system">cyber-physical systems</a>, and <a href="Dataflow_programming" title="Dataflow programming">dataflow programs</a>. TPT is specialised on testing and <a href="Verification_and_validation_(software)" class="mw-redirect" title="Verification and validation (software)">validation</a> of embedded systems whose inputs and outputs can be represented as <a href="Signal_(electrical_engineering)" class="mw-redirect" title="Signal (electrical engineering)">signals</a> and is a dedicated method for testing continuous behaviour of <a href="System" title="System">systems</a>.<sup id="cite_ref-fraunhofer2007_1-0" class="reference"><a href="#cite_note-fraunhofer2007-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Most <a href="Control_system" title="Control system">control systems</a> belong to this system class. The outstanding characteristic of control systems is the fact that they interact closely interlinked with a real world environment. Controllers need to observe their environment and react correspondingly to its behaviour.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> The system works in an interactional cycle with its environment and is subject to temporal constraints. Testing these systems is to stimulate and to check the timing behaviour. Traditional functional testing methods use scripts – TPT uses <a href="Model-based_testing" title="Model-based testing">model-based testing</a>.

</p><p>TPT combines a systematic and graphic modelling technique for test cases with a fully automated test execution in different environments and automatic test evaluation. TPT covers the following four test activities:

</p>

<ul><li><a href="Model-based_testing" title="Model-based testing">test case modelling</a></li>

<li>test execution in different environments (automated)</li>

<li>test result analysis (test assessment (automated))</li>

<li><a href="Software_Test_Documentation" class="mw-redirect" title="Software Test Documentation">test documentation</a> (automated)</li>

<li><a href="Test_management" title="Test management">test management</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Graphic_test_cases">Graphic test cases</h2></div>

<p>In TPT tests are modelled graphically with the aid of special state machines and time partitioning.<sup id="cite_ref-fraunhofer2007_1-1" class="reference"><a href="#cite_note-fraunhofer2007-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> All test cases for one system under test can be modelled using one hybrid automaton. Tests often consist of a sequence of logical phases. The <a href="State_(computer_science)" title="State (computer science)">states</a> of the <a href="Finite-state_machine" title="Finite-state machine">finite-state machine</a> represent the logical passes of a test which are similar for all tests. Trigger conditions model the transitions between the test phases. Each state and transition of the automaton may have different variants. The combination of the variants model the individual test cases.

</p><p><a href="Natural_language" title="Natural language">Natural language</a> texts become part of the graphics, supporting the simple and demonstrative readability even for non-programmers. Substantial techniques such as parallel and hierarchical branching <a href="Finite-state_machine" title="Finite-state machine">state machines</a>, conditional branching, <a href="Reactive_programming" title="Reactive programming">reactivity</a>, signal description, <a href="Measurement" title="Measurement">measured</a> signals as well as lists of simple test steps allow an intuitive and graphic modelling even of complex test cases.

</p><p>The test's complexity is hidden behind graphics. The lowest level signal description consists of either test step lists or so called direct definitions.

</p>

<div class="mw-heading mw-heading3"><h3 id="Modelling_simple_sequences:_Test-Step_List">Modelling simple sequences: Test-Step List</h3></div>

<p>Through the use of the Test-Step List, one can model simple sequences of test steps that do not need to execute in parallel, such as setting signals (Set channel), ramping signals (Ramp channel), setting parameters (Set parameter), and waiting (Wait). Requests for the expected test results can be made within the test sequence to evaluate the system under test as it runs. It is also possible to place subautomatons in the Test-Step List, which in turn contain automatons and sequences, resulting in hierarchical Test-Step Lists. The test sequences can also be combined with other modelling methods, allowing for a great deal of complexity (or simplicity) in one's test. Test sequences can also be combined and parallelised with other modelling methods.

</p>

<div class="mw-heading mw-heading3"><h3 id="Direct_signal_definition:_Direct_Definition">Direct signal definition: Direct Definition</h3></div>

<p>Within the Test-Step-List it is possible to implement so-called "Direct Definitions". Using this type of modelling, one can define signals as a function of time, past variables/test events, and other signals. It is also possible to define these signals by writing "<a href="C_(programming_language)" title="C (programming language)">C</a>-Style" code as well as importing measurement data and using a manual signal editor.

</p>

<div class="mw-heading mw-heading3"><h3 id="Functions">Functions</h3></div>

<p>It is possible to define <a href="Function_(programming)" class="mw-redirect" title="Function (programming)">functions</a> that can act as a <a href="Client_(computing)" title="Client (computing)">clients</a> or <a href="Server_(computing)" title="Server (computing)">servers</a>. Client functions are called from TPT in the system under test, where server functions implemented in TPT can be called as "<a href="Method_stub" title="Method stub">stub</a> functions" from the system under test. TPT itself may also call the server functions.

</p>

<div class="mw-heading mw-heading3"><h3 id="Systematic_test_cases">Systematic test cases</h3></div>

<p>TPT was developed specifically for testing of continuous and reactive behaviour of embedded systems.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> TPT can be seen as the extension of the <a href="Classification_Tree_Method" title="Classification Tree Method">Classification Tree Method</a> in terms of timing behaviour. Because of its systematic approach in <a href="Test_case" title="Test case">test case</a> generation, TPT even keeps track of very complex systems whose thorough testing requires a large number of test cases thus making it possible to find failures in the system under test with an ideal number of test cases.

</p><p>The underlying idea of TPT's systematic is the separation of similarities and differences among the test cases: most test cases are very similar in their structural process and can "only" be differentiated in a few, but crucial details.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> TPT makes use of this fact by jointly modelling and using joint structures. On the one hand, redundancies are thus avoided. On the other hand, it is made very clear what the test cases actually differ in – i.e. which specific aspect they respectively test. The comparability of test cases and thus the overview is improved in this approach and the attention of the tester is focused on the essential – the differentiating features of the test cases.

</p><p>The hierarchical structure of the test cases makes it possible to break complex test problems down into sub-problems thus also improving the clarity and – as a result – the quality of the test.

</p><p>These modelling techniques support the tester in finding the actually relevant cases, avoiding redundancies and keeping track of even large numbers of test cases.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Automatic_test_case_generation">Automatic test case generation</h3></div>

<p>TPT comprises several possibilities to automatically generate test cases:

</p>

<ul><li>test cases from equivalence classes</li>

<li>test cases for the coverage of <a href="Simulink" title="Simulink">Simulink</a> models by using static analysis and a search-based method<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup></li>

<li>test cases by building <a href="Sequence" title="Sequence">sequence</a> from variants of states and transitions of a test model</li>

<li>test cases by transforming recordings of user interactions with the system under test via a graphical user interface (Dashboard)</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Reactive_tests">Reactive tests</h3></div>

<p>With TPT, each test case can specifically react to the system's behaviour<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> during the testing process in real time – for instance to react on the system exactly when a certain system-state occurs or a sensor signal exceeds a certain threshold. If, for example, a sensor failure for an engine controller is to be simulated when the engine idling speed is exceeded, it has to be possible to react to the event "engine idling speed exceeded" in the description of the test case.

</p>

<div class="mw-heading mw-heading2"><h2 id="Test_execution">Test execution</h2></div>

<p>TPT test cases are made independent of its execution. The test cases can be executed in almost any environment due to the so-called <a href="Virtual_machine" title="Virtual machine">virtual machine</a> (VM) concept also in <a href="Real-time_computing" title="Real-time computing">real time</a> environments. Examples are <a href="MATLAB" title="MATLAB">MATLAB</a>/<a href="Simulink" title="Simulink">Simulink</a>, <a href="TargetLink" title="TargetLink">TargetLink</a>, ASCET, <a href="C_(programming_language)" title="C (programming language)">C-code</a>, <a href="Controller_Area_Network" class="mw-redirect" title="Controller Area Network">CAN</a>, <a href="AUTOSAR" title="AUTOSAR">AUTOSAR</a>, SystemDesk, DaVinci CT, LABCAR, INCA, Software-in-the-Loop (SiL) and <a href="Hardware-in-the-loop_simulation" title="Hardware-in-the-loop simulation">HiL</a>. Thus TPT is an integrated tool to be used in all testing phases of the development like <a href="Unit_testing" title="Unit testing">unit testing</a>, <a href="Integration_testing" title="Integration testing">integration testing</a>, <a href="System_testing" title="System testing">system testing</a> and <a href="Regression_testing" title="Regression testing">regression testing</a>.

</p><p>For analysis and measurement of <a href="Code_coverage" title="Code coverage">code coverage</a>, TPT can interact with coverage tools like Testwell CTC++ for <a href="C_(programming_language)" title="C (programming language)">C-code</a>.

</p><p>A configurable graphical user interface (Dashboard), based on <a href="Graphical_control_element" class="mw-redirect" title="Graphical control element">GUI widgets</a>, can be used to interact with tests.

</p>

<div class="mw-heading mw-heading3"><h3 id="TPT_virtual_machine">TPT virtual machine</h3></div>

<p>The modelled test cases in TPT are compiled and during test execution interpreted by the so-called <a href="Virtual_machine" title="Virtual machine">virtual machine</a> (VM). The VM is the same for all platforms and all tests. Only a platform <a href="Adapter" title="Adapter">adapter</a> realises the signal mapping for the individual application. The TPT-VM is implemented in <a href="ANSI_C" title="ANSI C">ANSI C</a> and requires a memory of just a few kilobytes and can completely do without a dynamic memory allocation, allowing it to be applied in minimalist and environments with few resources too. There are also <a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">APIs</a> for <a href="C_(programming_language)" title="C (programming language)">C</a> and <a href=".NET_Framework" title=".NET Framework">.NET</a>.

</p><p>TPT's Virtual Machine is able to process tests in real time with defined response behaviour. The response times of TPT test cases are normally given within micro seconds – depending on the complexity and test hardware.

</p>

<div class="mw-heading mw-heading2"><h2 id="Programmed_test_assessment">Programmed test assessment</h2></div>

<p>The expected system behaviour for individual test cases should also be automatically tested to assure efficient test processes. TPT offers the possibility to compute the properties for the expected behaviour online (during test execution) and offline (after test execution). While online evaluation uses the same modelling techniques as test modelling, offline evaluation offers decidedly more far-reaching possibilities for more complex evaluations, including operations such as comparisons with external reference data, limit-value monitoring, signal filters, analyses of state sequences and time conditions.

</p><p>The offline evaluation is, technically speaking, based on the <a href="Python_(programming_language)" title="Python (programming language)">Python</a> script language, which has been extended by specific syntactic language elements and a specialised evaluation library to give optimal support to the test evaluation. The use of a script language ensures a high degree of flexibility in the test evaluation: access to reference data, communication with other tools and development of one's own domain-specific libraries for test evaluation is supported. Besides of the script based test result evaluation user interfaces provide simple access to the test assessments and help non-programmers to avoid scripting.

</p><p>Measurement data from other sources like <i><a href="TargetLink" title="TargetLink">TargetLink</a></i> and <i><a href="Simulink" title="Simulink">Simulink</a></i> signal logging or MCD-3 measurement data can be assessed automatically. This data can be independent from the test execution.

</p>

<div class="mw-heading mw-heading2"><h2 id="Test_documentation">Test documentation</h2></div>

<p>TPT test documentation according to <a href="IEEE_829" class="mw-redirect" title="IEEE 829">IEEE 829</a> presents the result of the test evaluation to the tester in a HTML, report, in which not only the pure information "success", "failed" or "unknown" can be depicted as the test result for each test case, but also details such as characteristic parameters or signals that have been observed in the test execution or computed in the test evaluation. Since the test assessment returns proper information about the timing and the checked behaviour this information can be made available in the report.

The content of the test documentation as well as the structure of the document can be freely configured with the help of a template.

</p>

<div class="mw-heading mw-heading2"><h2 id="Test_management">Test management</h2></div>

<p>TPT supports <a href="Test_management" title="Test management">test management</a> of TPT test projects with the following activities:

</p>

<ul><li>Test case development in a test project</li>

<li>Test planning through test set configuration and test execution configuration</li>

<li>Automatic test execution and evaluation (assessment) in a Test campaign</li>

<li>Test reporting (detailed for an individual test run)</li>

<li>Test summary reporting over different release cycles and</li>

<li>Traceability of requirements, tests, test runs, test results</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Requirements_tracing">Requirements tracing</h2></div>

<p>Industry norms such as <a href="IEC_61508" title="IEC 61508">IEC 61508</a>, <a href="DO-178B" title="DO-178B">DO-178B</a>, EN 50128 and <a href="ISO_26262" title="ISO 26262">ISO 26262</a> require <a href="Requirements_traceability" title="Requirements traceability">traceability of requirements and tests</a>. TPT offers an interface to <a href="Requirement" title="Requirement">requirements</a> tools like <a href="Telelogic" title="Telelogic">Telelogic</a> DOORS to support these activities.

</p>

<div class="mw-heading mw-heading2"><h2 id="Application">Application</h2></div>

<p>TPT is a <a href="Model-based_testing" title="Model-based testing">model-based testing</a> <a href="Model-based_testing_tools" class="mw-redirect" title="Model-based testing tools">tool</a> and is applied mainly in the automotive controller development<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> and has originally been developed within <a href="Daimler_AG" class="mw-redirect" title="Daimler AG">Daimler AG</a> for their own development. Daimler coordinated the development of the testing tool for years.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> Since 2007 PikeTec continues the development of the tool. TPT is used by many different other car manufacturers like <a href="BMW" title="BMW">BMW</a>, <a href="Volkswagen" title="Volkswagen">Volkswagen</a>, <a href="Audi" title="Audi">Audi</a>, <a href="Porsche" title="Porsche">Porsche</a> and <a href="General_Motors" title="General Motors">General Motors</a> as well as suppliers like <a href="Robert_Bosch_GmbH" class="mw-redirect" title="Robert Bosch GmbH">Robert Bosch GmbH</a>, <a href="Continental_AG" title="Continental AG">Continental</a> and <a href="Hella_(company)" title="Hella (company)">Hella</a>.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120302044506/http://www.fokus.fraunhofer.de/de/motion/ueber_motion/unser_team/zander_justyna/Conquest_07_vfinal_DV2.pdf">"Justyna Zander-Nowicka, Abel Marrero Pérez, Ina Schieferdecker, Zhen Ru Dai: Test Design Patterns for Embedded Systems, In: 10th International Conference on Quality Engineering in Software Technology, CONQUEST 2007, Potsdam, Germany, September 2007"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="http://www.fokus.fraunhofer.de/de/motion/ueber_motion/unser_team/zander_justyna/Conquest_07_vfinal_DV2.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2012-03-02<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-08-08</span></span>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFKarl_J._Åström_and_Richard_M._Murray2008" class="citation book cs1">Karl J. Åström and Richard M. Murray (2008). <a rel="nofollow" class="external text" href="http://www.cds.caltech.edu/~murray/books/AM08/pdf/am08-complete_22Feb09.pdf"><i>Feedback Systems: An Introduction for Scientists and Engineers</i></a> <span class="cs1-format">(PDF)</span>. Princeton University Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-691-13576-2</bdi>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.irisa.fr/lande/lande/icse-proceedings/seas/p29.pdf">"Schieferdecker, Bringmann, Grossmann: Continuous TTCN-3: Testing of Embedded Control Systems, In: Proceedings of 28th International Conference on Software Engineering, Shanghai, China, 2006"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">2013-08-08</span></span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://piketec.com/downloads/papers/bringmann-kraemer-systematic-testing-of-the-continuous-behavior-of-automotive-systems.pdf">"Bringmann, Krämer: Systematic testing of the continuous behavior of automotive systems In: International Conference on Software Engineering: Proceedings of the 2006 international workshop on Software, Shanghai, China, 2006"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">2013-08-08</span></span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.piketec.com/downloads/papers/ELehmannDissertation.pdf">"Lehmann, TPT – Dissertation, 2003"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">2013-08-08</span></span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://evotest.iti.upv.es/index.php?option=com_docman&task=doc_view&gid=29&Itemid=70">"Lehmann: Time Partition Testing: A Method for Testing Dynamical Functional Behavior IN: Proceedings of Test2000, Lindon, Great Britain, 2000"</a>. Evotest.iti.upv.es<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-08-08</span></span>.</cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text">Benjamin Wilmes: <i>Hybrides Testverfahren für Simulink/TargetLink-Modelle</i>, Dissertation, TU-Berlin, Germany, 2015. <a rel="nofollow" class="external autonumber" href="https://opus4.kobv.de/opus4-tuberlin/frontdoor/index/index/docId/6377">[1]</a></span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.immos-project.de/site_immos/download/TestML_Semantics.pdf">"Grossmann, Müller: A Formal Behavioral Semantics for TestML; In:Proc. of ISOLA 06, Paphos, Cyprus, November 2006"</a> <span class="cs1-format">(PDF)</span>. Immos-project.de.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFBringmannKrämer2008" class="citation conference cs1">Bringmann, E.; Krämer, A. (2008). <a rel="nofollow" class="external text" href="http://www.piketec.com/downloads/papers/Kraemer2008-Model_based_testing_of_automotive_systems.pdf">"Model-Based Testing of Automotive Systems"</a> <span class="cs1-format">(PDF)</span>. <i>2008 International Conference on Software Testing, Verification, and Validation</i>. International Conference on Software Testing, Verification, and Validation (ICST). pp. <span class="nowrap">485–</span>493. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FICST.2008.45">10.1109/ICST.2008.45</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7695-3127-4</bdi>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite id="CITEREFConradFeyGrochtmannKlein2001" class="citation journal cs1">Conrad, Mirko; Fey, Ines; Grochtmann, Matthias; Klein, Torsten (2001-07-09). "Modellbasierte Entwicklung eingebetteter Fahrzeugsoftware bei DaimlerChrysler". <i>Informatik - Forschung und Entwicklung</i>. <b>20</b> (<span class="nowrap">1–</span>2): <span class="nowrap">3–</span>10. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs00450-005-0197-5">10.1007/s00450-005-0197-5</a>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.hanser-automotive.de/aktuelle-entwicklungswerkzeuge/entwicklungswerkzeuge/article/piketec-tpt-als-test-und-verifikationssoftware.html">Hauser Automotive Website. Retrieved 16 March 2015</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20151124224530/http://www.hanser-automotive.de/aktuelle-entwicklungswerkzeuge/entwicklungswerkzeuge/article/piketec-tpt-als-test-und-verifikationssoftware.html">Archived</a> 2015-11-24 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

This article is issued from <a class="external text" title="Last edited on 2025-01-20" href="https://en.wikipedia.org/wiki/?title=TPT_(software)&oldid=1270607151">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>